Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56dcbe04596d83bf6fcc57f8ec6381450ee936a947bed114e999a39b771c22d3

Tx prefix hash: 8dcdfb3cd6e71e522a356d13b14d971357293595acdfd276b5a56ab91b4417e5
Tx public key: 2f06fe0afe6ed9bcc52453dc4b2b36894df21cfbf3dc882a24b5c1a90b411203
Timestamp: 1701639988 Timestamp [UCT]: 2023-12-03 21:46:28 Age [y:d:h:m:s]: 01:044:18:12:45
Block: 905337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293364 RingCT/type: yes/0
Extra: 012f06fe0afe6ed9bcc52453dc4b2b36894df21cfbf3dc882a24b5c1a90b41120302110000000675e3f0e9000000000000000000

1 output(s) for total of 0.614105054000 dcy

stealth address amount amount idx
00: c90f04188cecf9b4ca7700eec5222a292f32aa325b5cd7b2dfa47b9d87ff54a1 0.614105054000 1362220 of 0

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": 905347, "vin": [ { "gen": { "height": 905337 } } ], "vout": [ { "amount": 614105054, "target": { "key": "c90f04188cecf9b4ca7700eec5222a292f32aa325b5cd7b2dfa47b9d87ff54a1" } } ], "extra": [ 1, 47, 6, 254, 10, 254, 110, 217, 188, 197, 36, 83, 220, 75, 43, 54, 137, 77, 242, 28, 251, 243, 220, 136, 42, 36, 181, 193, 169, 11, 65, 18, 3, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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