Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 218256a5ad0eaf3884a7c8627d20935553bcf6fde230e227381f32eb96237d67

Tx prefix hash: 3977844d18cd935194f3faf2783c714b4824351907e442b4395a079d3d169f53
Tx public key: 4ce5a731ea7b4f1fef68309d3c246f63a8e831f131951cc26b7676f242a84882
Timestamp: 1717479413 Timestamp [UCT]: 2024-06-04 05:36:53 Age [y:d:h:m:s]: 00:334:00:43:47
Block: 1036668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238731 RingCT/type: yes/0
Extra: 014ce5a731ea7b4f1fef68309d3c246f63a8e831f131951cc26b7676f242a848820211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28bb6641315c6f52fa74ba883aa7d9f7e977e89ef2e4f281110b0612fe01dc5c 0.600000000000 1505197 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": 1036678, "vin": [ { "gen": { "height": 1036668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28bb6641315c6f52fa74ba883aa7d9f7e977e89ef2e4f281110b0612fe01dc5c" } } ], "extra": [ 1, 76, 229, 167, 49, 234, 123, 79, 31, 239, 104, 48, 157, 60, 36, 111, 99, 168, 232, 49, 241, 49, 149, 28, 194, 107, 118, 118, 242, 66, 168, 72, 130, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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