Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cfbbf0c2ba8cd36e796bee91941205845a771b371ab4981060b290f94576bd4

Tx prefix hash: 4979c186013f5c235bbe5d895a753ac97310956489d6a07b3f2ec253f1e169d4
Tx public key: afd14dbbd43aad3dcb9b8b941add800234a3302a4b84a5f4d1838af211586cc5
Timestamp: 1709858046 Timestamp [UCT]: 2024-03-08 00:34:06 Age [y:d:h:m:s]: 01:076:08:22:55
Block: 973487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315595 RingCT/type: yes/0
Extra: 01afd14dbbd43aad3dcb9b8b941add800234a3302a4b84a5f4d1838af211586cc50211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b4978e59aa6ae024786b328cb3e8faee929e607e03380ab0f3ac9e2a108fad1 0.600000000000 1433422 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": 973497, "vin": [ { "gen": { "height": 973487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b4978e59aa6ae024786b328cb3e8faee929e607e03380ab0f3ac9e2a108fad1" } } ], "extra": [ 1, 175, 209, 77, 187, 212, 58, 173, 61, 203, 155, 139, 148, 26, 221, 128, 2, 52, 163, 48, 42, 75, 132, 165, 244, 209, 131, 138, 242, 17, 88, 108, 197, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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