Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37b42890a3db123b11defaec5960626aea4b5510d4df2d5a99992a8895e4941b

Tx prefix hash: 6ecccf9c877f67ed96d7799a683e2c25b9e49aa885fe96ca53a530ed02b7b3e6
Tx public key: cc2d23a30db895ea705b5afe83c64eedd63c0ce8b655022836a31cd3c7e85d1c
Timestamp: 1708287581 Timestamp [UCT]: 2024-02-18 20:19:41 Age [y:d:h:m:s]: 01:263:10:04:41
Block: 960457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447004 RingCT/type: yes/0
Extra: 01cc2d23a30db895ea705b5afe83c64eedd63c0ce8b655022836a31cd3c7e85d1c02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32c2c792b2ac89f29ccae250d9cef5e3627c9520398f941d56f6169426efcebe 0.600000000000 1420022 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": 960467, "vin": [ { "gen": { "height": 960457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32c2c792b2ac89f29ccae250d9cef5e3627c9520398f941d56f6169426efcebe" } } ], "extra": [ 1, 204, 45, 35, 163, 13, 184, 149, 234, 112, 91, 90, 254, 131, 198, 78, 237, 214, 60, 12, 232, 182, 85, 2, 40, 54, 163, 28, 211, 199, 232, 93, 28, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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