Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0bb71717db0f736d17d0baeea697019036d195352d0c1c757b11b1eb0df1bdd

Tx prefix hash: 573df90580a60aa0ce004039bac2832b0e1fea441c9795adb7282672b82d2706
Tx public key: 46b6a9ffb8b18338a3e83ce9554f4f0e2708cbdd23899f8e3786e46e1e812780
Timestamp: 1701046065 Timestamp [UCT]: 2023-11-27 00:47:45 Age [y:d:h:m:s]: 01:137:15:52:57
Block: 900413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359557 RingCT/type: yes/0
Extra: 0146b6a9ffb8b18338a3e83ce9554f4f0e2708cbdd23899f8e3786e46e1e81278002110000000a33af99f4000000000000000000

1 output(s) for total of 0.637614133000 dcy

stealth address amount amount idx
00: 7b5d3e59b9edafb6a504e7b60e4b06bcd87b4b826a9d87150feb54c3d2c1fba1 0.637614133000 1356914 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": 900423, "vin": [ { "gen": { "height": 900413 } } ], "vout": [ { "amount": 637614133, "target": { "key": "7b5d3e59b9edafb6a504e7b60e4b06bcd87b4b826a9d87150feb54c3d2c1fba1" } } ], "extra": [ 1, 70, 182, 169, 255, 184, 177, 131, 56, 163, 232, 60, 233, 85, 79, 79, 14, 39, 8, 203, 221, 35, 137, 159, 142, 55, 134, 228, 110, 30, 129, 39, 128, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 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