Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92974d83ed4bea49fd7df57064a09a6737358fdd60c4c9170e13eded419720ca

Tx prefix hash: 5ecc22fdd9a12f9dacb4a436670480a2212641bd3529d8e5d62cb8160b959e15
Tx public key: 140c18ff5b48dc8bcf9c394964ac1bca13969def9d208bbc201c7f1e9c8cc6bb
Timestamp: 1735139875 Timestamp [UCT]: 2024-12-25 15:17:55 Age [y:d:h:m:s]: 00:088:11:56:39
Block: 1182954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63020 RingCT/type: yes/0
Extra: 01140c18ff5b48dc8bcf9c394964ac1bca13969def9d208bbc201c7f1e9c8cc6bb0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9774f1459070747a48a2eb96cae3fe9c8cac77cbb580d318e397542fc9dfb635 0.600000000000 1669393 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": 1182964, "vin": [ { "gen": { "height": 1182954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9774f1459070747a48a2eb96cae3fe9c8cac77cbb580d318e397542fc9dfb635" } } ], "extra": [ 1, 20, 12, 24, 255, 91, 72, 220, 139, 207, 156, 57, 73, 100, 172, 27, 202, 19, 150, 157, 239, 157, 32, 139, 188, 32, 28, 127, 30, 156, 140, 198, 187, 2, 17, 0, 0, 0, 8, 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