Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f37d53d4cc27f2319d4ad85d3a27a582a4cabc3b7cc0ab935f1f9875c2fa0396

Tx prefix hash: 8f8764655542e9670c580a1983eba1a9ef79cbc482ad352dede73eb161d63c55
Tx public key: 7b70f434e082a09c304f1d560a0ba02fbdd78a2cd5887cc5815fdac2939917e6
Timestamp: 1727032418 Timestamp [UCT]: 2024-09-22 19:13:38 Age [y:d:h:m:s]: 00:122:04:48:05
Block: 1115860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87337 RingCT/type: yes/0
Extra: 017b70f434e082a09c304f1d560a0ba02fbdd78a2cd5887cc5815fdac2939917e6021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a92eddd9f366737ce0a5b6979e1551fe2952afdceef4bc9877a7dc9347e9e1d2 0.600000000000 1596137 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": 1115870, "vin": [ { "gen": { "height": 1115860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a92eddd9f366737ce0a5b6979e1551fe2952afdceef4bc9877a7dc9347e9e1d2" } } ], "extra": [ 1, 123, 112, 244, 52, 224, 130, 160, 156, 48, 79, 29, 86, 10, 11, 160, 47, 189, 215, 138, 44, 213, 136, 124, 197, 129, 95, 218, 194, 147, 153, 23, 230, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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