Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4b1f7bb110b0c7ca800157c8adac6e436d48da4266c408a22c30cf620a46d1f

Tx prefix hash: ce162f647636b4eef338c12478b457d25c72599c9e8d49e680f081c8fa5f7b35
Tx public key: 424975b165e5d961ddfb6dc9c64293362030359c75c6acecdcf61b3650ff3b5a
Timestamp: 1735051588 Timestamp [UCT]: 2024-12-24 14:46:28 Age [y:d:h:m:s]: 00:084:19:52:05
Block: 1182230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60418 RingCT/type: yes/0
Extra: 01424975b165e5d961ddfb6dc9c64293362030359c75c6acecdcf61b3650ff3b5a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff593ddb7db3ae7314e45414e2034f494fdcaf17fbe0fd1d2489904eeafff1a9 0.600000000000 1668663 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": 1182240, "vin": [ { "gen": { "height": 1182230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff593ddb7db3ae7314e45414e2034f494fdcaf17fbe0fd1d2489904eeafff1a9" } } ], "extra": [ 1, 66, 73, 117, 177, 101, 229, 217, 97, 221, 251, 109, 201, 198, 66, 147, 54, 32, 48, 53, 156, 117, 198, 172, 236, 220, 246, 27, 54, 80, 255, 59, 90, 2, 17, 0, 0, 0, 3, 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