Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fbfe159a9b8287489880066abdac4664f4f73e3c0f9a8eb25f659a4e0991180

Tx prefix hash: e769c2ec0548e513f9412ccba51e1df450282a7cd273d259d4c4b4edeca94a27
Tx public key: d205f4478fcd7124b81b0af1ac259b6630af3d0d1bc9623979b34de842bb7e3f
Timestamp: 1716528296 Timestamp [UCT]: 2024-05-24 05:24:56 Age [y:d:h:m:s]: 00:243:17:29:50
Block: 1028783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174382 RingCT/type: yes/0
Extra: 01d205f4478fcd7124b81b0af1ac259b6630af3d0d1bc9623979b34de842bb7e3f02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec8ce3c33a33988cba35c9ce443e89bb89540dbe13694e3a24e3b2b8cb2fd434 0.600000000000 1496780 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": 1028793, "vin": [ { "gen": { "height": 1028783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec8ce3c33a33988cba35c9ce443e89bb89540dbe13694e3a24e3b2b8cb2fd434" } } ], "extra": [ 1, 210, 5, 244, 71, 143, 205, 113, 36, 184, 27, 10, 241, 172, 37, 155, 102, 48, 175, 61, 13, 27, 201, 98, 57, 121, 179, 77, 232, 66, 187, 126, 63, 2, 17, 0, 0, 0, 4, 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