Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be45f1cebbe43ed726f6b7b72f2016cc0f7797bbaca33bb035fd45586139ee53

Tx prefix hash: 1db452d6e40acb43ae827e5541854b04478e53980a8e7f1fd6bf4eba964a24c7
Tx public key: c5bdf31749929e30245b29e9e4971ea545cb6cd1b89a78b5f50faeb8a626d2ad
Timestamp: 1646144891 Timestamp [UCT]: 2022-03-01 14:28:11 Age [y:d:h:m:s]: 03:305:17:21:26
Block: 449113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 996349 RingCT/type: yes/0
Extra: 01c5bdf31749929e30245b29e9e4971ea545cb6cd1b89a78b5f50faeb8a626d2ad02110000003f4da16a3a000000000000000000

1 output(s) for total of 19.948143117000 dcy

stealth address amount amount idx
00: 6d8d3c882484f973d51c80f67fdc42cf264cfdb29294824251dd95824f5b3bd4 19.948143117000 863638 of 0

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": 449123, "vin": [ { "gen": { "height": 449113 } } ], "vout": [ { "amount": 19948143117, "target": { "key": "6d8d3c882484f973d51c80f67fdc42cf264cfdb29294824251dd95824f5b3bd4" } } ], "extra": [ 1, 197, 189, 243, 23, 73, 146, 158, 48, 36, 91, 41, 233, 228, 151, 30, 165, 69, 203, 108, 209, 184, 154, 120, 181, 245, 15, 174, 184, 166, 38, 210, 173, 2, 17, 0, 0, 0, 63, 77, 161, 106, 58, 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