Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05ed3fe71c38e5c27f7f588143b2709e8158f0d884aeaa79477e772c57bbfb25

Tx prefix hash: 37773043c7a6087a28d9b36161de0cad53cb3d3665d00e41828ac1e6446a9883
Tx public key: 84d50d561a971bf98d1d34314dd959f32a5439180692c8ca4eef1cbc2216dcf4
Timestamp: 1736024268 Timestamp [UCT]: 2025-01-04 20:57:48 Age [y:d:h:m:s]: 01:026:08:38:13
Block: 1190275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277123 RingCT/type: yes/0
Extra: 0184d50d561a971bf98d1d34314dd959f32a5439180692c8ca4eef1cbc2216dcf402110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8358562533be2a76f5ceb4fada39256a7a6b24c57f8a6f5940e701ed8c6f4e6 0.600000000000 1676790 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": 1190285, "vin": [ { "gen": { "height": 1190275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8358562533be2a76f5ceb4fada39256a7a6b24c57f8a6f5940e701ed8c6f4e6" } } ], "extra": [ 1, 132, 213, 13, 86, 26, 151, 27, 249, 141, 29, 52, 49, 77, 217, 89, 243, 42, 84, 57, 24, 6, 146, 200, 202, 78, 239, 28, 188, 34, 22, 220, 244, 2, 17, 0, 0, 0, 12, 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