Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f120d912d41c8b6d9d64387462e7cc0896e0e103eb02057becefe05c8ebd3c2

Tx prefix hash: f5305fafb2425d997030640c733e3b2777259f450a7466c9a08ee5c8988d41dc
Tx public key: a4d7399485c2bb656a11a0b1f028d30feb4dc2f11ad57952be977c7be9bbb0d3
Timestamp: 1725181251 Timestamp [UCT]: 2024-09-01 09:00:51 Age [y:d:h:m:s]: 01:067:21:55:44
Block: 1100514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306966 RingCT/type: yes/0
Extra: 01a4d7399485c2bb656a11a0b1f028d30feb4dc2f11ad57952be977c7be9bbb0d3021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f02ef9e1d63b1d6c8b5efb936d4c43846b6d24b733c462d2dc90c9aa5a8271f 0.600000000000 1576493 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": 1100524, "vin": [ { "gen": { "height": 1100514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f02ef9e1d63b1d6c8b5efb936d4c43846b6d24b733c462d2dc90c9aa5a8271f" } } ], "extra": [ 1, 164, 215, 57, 148, 133, 194, 187, 101, 106, 17, 160, 177, 240, 40, 211, 15, 235, 77, 194, 241, 26, 213, 121, 82, 190, 151, 124, 123, 233, 187, 176, 211, 2, 17, 0, 0, 0, 3, 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