Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6f31d6a1d4412a37297cd0527a3c97d420aac17bf9becab20028f20b9841d60

Tx prefix hash: e3bb25eb487aba9e631672fff71455dacdac1f1eaa65967fff0ec65bc3a85db1
Tx public key: 21858b1e584a73acecad0fbcd3bb5c8d893f5aa90bdde3440478040a8af905ae
Timestamp: 1727407600 Timestamp [UCT]: 2024-09-27 03:26:40 Age [y:d:h:m:s]: 00:245:23:45:12
Block: 1118967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175659 RingCT/type: yes/0
Extra: 0121858b1e584a73acecad0fbcd3bb5c8d893f5aa90bdde3440478040a8af905ae021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c138ae670f878d98c07fa1ea2c2406958e4c87122e4460c8b50c4a66c31c7d6d 0.600000000000 1600346 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": 1118977, "vin": [ { "gen": { "height": 1118967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c138ae670f878d98c07fa1ea2c2406958e4c87122e4460c8b50c4a66c31c7d6d" } } ], "extra": [ 1, 33, 133, 139, 30, 88, 74, 115, 172, 236, 173, 15, 188, 211, 187, 92, 141, 137, 63, 90, 169, 11, 221, 227, 68, 4, 120, 4, 10, 138, 249, 5, 174, 2, 17, 0, 0, 0, 6, 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