Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b27b3231bd0791b6d43ea11d167c793db0ca709ea4de430b93d9236f5237705f

Tx prefix hash: 363b8753aed8b1dfdd9b979cbb7a9601616922d69c970edab492b25abfe21358
Tx public key: ff951ddabfa3e7e36f1f2f2ef0e5294cb1899e538e34bbd2b7ba4776b03f9310
Timestamp: 1711536825 Timestamp [UCT]: 2024-03-27 10:53:45 Age [y:d:h:m:s]: 00:293:15:56:25
Block: 987417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210183 RingCT/type: yes/0
Extra: 01ff951ddabfa3e7e36f1f2f2ef0e5294cb1899e538e34bbd2b7ba4776b03f931002110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fa16e6cabed6466d3e57199afe828c2b9ab417d44a7b1afd3af67d1dcc02293 0.600000000000 1447666 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": 987427, "vin": [ { "gen": { "height": 987417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fa16e6cabed6466d3e57199afe828c2b9ab417d44a7b1afd3af67d1dcc02293" } } ], "extra": [ 1, 255, 149, 29, 218, 191, 163, 231, 227, 111, 31, 47, 46, 240, 229, 41, 76, 177, 137, 158, 83, 142, 52, 187, 210, 183, 186, 71, 118, 176, 63, 147, 16, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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