Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f56afc10256a24defbb063c3ab9b7e86297db4f11a45f4edb93f0b2a348def4

Tx prefix hash: d69e0c988ebcd11d0aaa343145120cf28c5cc79cb2c9eb50a216c358b7d0c0fa
Tx public key: b4f775edc5959800bd455ce504ae06dfe1ba7cfc0536b91ca753c6de2a53c402
Timestamp: 1731786044 Timestamp [UCT]: 2024-11-16 19:40:44 Age [y:d:h:m:s]: 00:007:11:45:24
Block: 1155166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5369 RingCT/type: yes/0
Extra: 01b4f775edc5959800bd455ce504ae06dfe1ba7cfc0536b91ca753c6de2a53c402021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95b4e3a3ce513881df5e3440c80146b81439a931bda0a1140450a51bbe9f7887 0.600000000000 1640781 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": 1155176, "vin": [ { "gen": { "height": 1155166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95b4e3a3ce513881df5e3440c80146b81439a931bda0a1140450a51bbe9f7887" } } ], "extra": [ 1, 180, 247, 117, 237, 197, 149, 152, 0, 189, 69, 92, 229, 4, 174, 6, 223, 225, 186, 124, 252, 5, 54, 185, 28, 167, 83, 198, 222, 42, 83, 196, 2, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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