Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 271a812f3f1df8acd2b2c04e6cf147b543377a2bb57f53c12dde5e9499620eea

Tx prefix hash: 56da1a5c0649d57d08deacf0647e48e758c986a04652cce059988295f0bf062d
Tx public key: 2c31edf4b906ad157516e6f73ca021c683b1e88f9af896ca34578d48fd33e36b
Timestamp: 1718409530 Timestamp [UCT]: 2024-06-14 23:58:50 Age [y:d:h:m:s]: 00:223:06:36:47
Block: 1044370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159740 RingCT/type: yes/0
Extra: 012c31edf4b906ad157516e6f73ca021c683b1e88f9af896ca34578d48fd33e36b0211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98ec90c592bdbf36b28081a76473ea8d6fab0f87805620c2a618863e35703b44 0.600000000000 1513663 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": 1044380, "vin": [ { "gen": { "height": 1044370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98ec90c592bdbf36b28081a76473ea8d6fab0f87805620c2a618863e35703b44" } } ], "extra": [ 1, 44, 49, 237, 244, 185, 6, 173, 21, 117, 22, 230, 247, 60, 160, 33, 198, 131, 177, 232, 143, 154, 248, 150, 202, 52, 87, 141, 72, 253, 51, 227, 107, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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