Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f0fe301f3c8a3e93c7e20ca61f0e5fbd59fbb87c5c617264d125002d9f48468

Tx prefix hash: 9fb8ba07c6873a21cedb1a0f37a76743dbd33940bca124e8fb8286cfb3c69a52
Tx public key: a214ae00bcc2b6ced5da1e96944197317fdc01d189074397b2245db1ddd76711
Timestamp: 1720439908 Timestamp [UCT]: 2024-07-08 11:58:28 Age [y:d:h:m:s]: 00:273:14:46:34
Block: 1061212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195470 RingCT/type: yes/0
Extra: 01a214ae00bcc2b6ced5da1e96944197317fdc01d189074397b2245db1ddd76711021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6acfa5ac5c4c9b1445e3bbdc9129514cc13cb4efee15ced2d3f76bba80efecd3 0.600000000000 1531703 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": 1061222, "vin": [ { "gen": { "height": 1061212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6acfa5ac5c4c9b1445e3bbdc9129514cc13cb4efee15ced2d3f76bba80efecd3" } } ], "extra": [ 1, 162, 20, 174, 0, 188, 194, 182, 206, 213, 218, 30, 150, 148, 65, 151, 49, 127, 220, 1, 209, 137, 7, 67, 151, 178, 36, 93, 177, 221, 215, 103, 17, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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