Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 877cfe18b018321a2f8ce2e8a7bfaa3f6ad9a0a62dcccd867d1ecff17321d0a3

Tx prefix hash: 47971114198771cbebea42a9bfa3da74812c9a938cb85843e3a383ad0b7d58f0
Tx public key: e16848e1921c309cf953b94f64a3ac5c63d413afa7566e611515cf4d59b71bb5
Timestamp: 1734689894 Timestamp [UCT]: 2024-12-20 10:18:14 Age [y:d:h:m:s]: 00:019:11:47:10
Block: 1179250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13907 RingCT/type: yes/0
Extra: 01e16848e1921c309cf953b94f64a3ac5c63d413afa7566e611515cf4d59b71bb502110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29b74ecb289fbca5632be60f7076848f8446d6a37d448f8bb142f3d2e0ccf04b 0.600000000000 1665643 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": 1179260, "vin": [ { "gen": { "height": 1179250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29b74ecb289fbca5632be60f7076848f8446d6a37d448f8bb142f3d2e0ccf04b" } } ], "extra": [ 1, 225, 104, 72, 225, 146, 28, 48, 156, 249, 83, 185, 79, 100, 163, 172, 92, 99, 212, 19, 175, 167, 86, 110, 97, 21, 21, 207, 77, 89, 183, 27, 181, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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