Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3adc9bb92a179b564061f94f58972e064168fdc5ca07ad9eea0b21ac9d31998a

Tx prefix hash: 1ab626c5ca3e7072ec2916f6fcb6baa832af390e2acf988b1385e90954416513
Tx public key: feff5ab62b9f0710b3bc00ee43c64db80c9d80fbf5e38fed0eda5d5faf2c38f8
Timestamp: 1702115532 Timestamp [UCT]: 2023-12-09 09:52:12 Age [y:d:h:m:s]: 01:108:04:58:52
Block: 909278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338462 RingCT/type: yes/0
Extra: 01feff5ab62b9f0710b3bc00ee43c64db80c9d80fbf5e38fed0eda5d5faf2c38f8021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e497a99282e37ae764ea2341ff618fece84f0b2d58a13491fde55041e728b250 0.600000000000 1366349 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": 909288, "vin": [ { "gen": { "height": 909278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e497a99282e37ae764ea2341ff618fece84f0b2d58a13491fde55041e728b250" } } ], "extra": [ 1, 254, 255, 90, 182, 43, 159, 7, 16, 179, 188, 0, 238, 67, 198, 77, 184, 12, 157, 128, 251, 245, 227, 143, 237, 14, 218, 93, 95, 175, 44, 56, 248, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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