Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 186d217bd2d38dcd2e60e4426a7f8d22f9177af8242a1b548070ee26d602a207

Tx prefix hash: f818d4173197a17de19dd323a5eaac61a389cbbd96ac059c321c7524c7c1913a
Tx public key: bd7c63281c07944de7166abff3a8925112cae5093e1e4e7e57df8990398bc2fc
Timestamp: 1705015632 Timestamp [UCT]: 2024-01-11 23:27:12 Age [y:d:h:m:s]: 01:327:20:33:21
Block: 933305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493200 RingCT/type: yes/0
Extra: 01bd7c63281c07944de7166abff3a8925112cae5093e1e4e7e57df8990398bc2fc02110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f17fbe3abe7650bd1137aa85c00afb7016b29f51c6a001ae1af049d5ac30e6a 0.600000000000 1391267 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 933315, "vin": [ { "gen": { "height": 933305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f17fbe3abe7650bd1137aa85c00afb7016b29f51c6a001ae1af049d5ac30e6a" } } ], "extra": [ 1, 189, 124, 99, 40, 28, 7, 148, 77, 231, 22, 106, 191, 243, 168, 146, 81, 18, 202, 229, 9, 62, 30, 78, 126, 87, 223, 137, 144, 57, 139, 194, 252, 2, 17, 0, 0, 0, 14, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8