Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f87c3ea60bcd39d96908524090980f7b8e55fd7cead5ec7f62c65864090000fe

Tx prefix hash: b560a6a35aa26cbccc03663135ad1406e27be216270e0df4898d182898a316bc
Tx public key: fe70db91684c4bc7a791798ccb28ba84a9b71bf6a2810e543ea5db0d893e768d
Timestamp: 1715755017 Timestamp [UCT]: 2024-05-15 06:36:57 Age [y:d:h:m:s]: 01:180:13:29:30
Block: 1022360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387661 RingCT/type: yes/0
Extra: 01fe70db91684c4bc7a791798ccb28ba84a9b71bf6a2810e543ea5db0d893e768d02110000000152d47e94000000000000000000

1 output(s) for total of 0.615590000000 dcy

stealth address amount amount idx
00: 95617c5b193bdd30b4e43bbc49120225d10015e0a2b04c6b87b39a2460b580c0 0.615590000000 1486935 of 0

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": 1022370, "vin": [ { "gen": { "height": 1022360 } } ], "vout": [ { "amount": 615590000, "target": { "key": "95617c5b193bdd30b4e43bbc49120225d10015e0a2b04c6b87b39a2460b580c0" } } ], "extra": [ 1, 254, 112, 219, 145, 104, 76, 75, 199, 167, 145, 121, 140, 203, 40, 186, 132, 169, 183, 27, 246, 162, 129, 14, 84, 62, 165, 219, 13, 137, 62, 118, 141, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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