Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02e34af46602d060fb352aac036385270b32937dea3d9e34af589f5055716f3b

Tx prefix hash: 2b8da7c29f0503810377ea7180b5b094a4c2cde8b0262a4603a854e1b089635a
Tx public key: 549c1aefbe115ce7fc32d7d4107e34c3941dfd40f0d07e7978d3778d42666051
Timestamp: 1730689174 Timestamp [UCT]: 2024-11-04 02:59:34 Age [y:d:h:m:s]: 00:079:16:46:11
Block: 1146093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56969 RingCT/type: yes/0
Extra: 01549c1aefbe115ce7fc32d7d4107e34c3941dfd40f0d07e7978d3778d42666051021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: decc78c91c7940b2bce5799d4e8d213cfe9e0e29c84fd8f1b3cc94fc1b719004 0.600000000000 1630656 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": 1146103, "vin": [ { "gen": { "height": 1146093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "decc78c91c7940b2bce5799d4e8d213cfe9e0e29c84fd8f1b3cc94fc1b719004" } } ], "extra": [ 1, 84, 156, 26, 239, 190, 17, 92, 231, 252, 50, 215, 212, 16, 126, 52, 195, 148, 29, 253, 64, 240, 208, 126, 121, 120, 211, 119, 141, 66, 102, 96, 81, 2, 17, 0, 0, 0, 2, 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