Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bbd321a204257c18b78aca27070a613b50371f32680fc2d6899b65fff6d2872

Tx prefix hash: a26b19d28c53c8701a8007c4fe5cc5a59c4e445cdc1f403efa33bc78807d732c
Tx public key: 9f9516dcf8cb43fb7ac205afaaacd67978cf5fc29f39318d2b4ec5b0da711b27
Timestamp: 1737463381 Timestamp [UCT]: 2025-01-21 12:43:01 Age [y:d:h:m:s]: 00:148:17:33:46
Block: 1202145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106009 RingCT/type: yes/0
Extra: 019f9516dcf8cb43fb7ac205afaaacd67978cf5fc29f39318d2b4ec5b0da711b270211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9eb7f516fa06e7823ec895d151192c1092d12d07d8fcb912f1c4d3ae849aade 0.600000000000 1688804 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": 1202155, "vin": [ { "gen": { "height": 1202145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9eb7f516fa06e7823ec895d151192c1092d12d07d8fcb912f1c4d3ae849aade" } } ], "extra": [ 1, 159, 149, 22, 220, 248, 203, 67, 251, 122, 194, 5, 175, 170, 172, 214, 121, 120, 207, 95, 194, 159, 57, 49, 141, 43, 78, 197, 176, 218, 113, 27, 39, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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