Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc0bdcb1fb0a99392952941979ab6a7110f70127a20cc44305203d5a6d97970d

Tx prefix hash: 6ffe58e8b63280430d7407934fbd6625bea9ad0199fa9e2e3662394aa23b2e38
Tx public key: 7c1170f969f87f33a4401626d8e2a69bbf30e1c9f7bf204f6f2161ce02322fcf
Timestamp: 1702438945 Timestamp [UCT]: 2023-12-13 03:42:25 Age [y:d:h:m:s]: 01:119:19:16:57
Block: 911980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346745 RingCT/type: yes/0
Extra: 017c1170f969f87f33a4401626d8e2a69bbf30e1c9f7bf204f6f2161ce02322fcf021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b57e14350f84cf9de7117b442367b541a2dd178b89dc38fc43a1fa3f183b5d4 0.600000000000 1369198 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": 911990, "vin": [ { "gen": { "height": 911980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b57e14350f84cf9de7117b442367b541a2dd178b89dc38fc43a1fa3f183b5d4" } } ], "extra": [ 1, 124, 17, 112, 249, 105, 248, 127, 51, 164, 64, 22, 38, 216, 226, 166, 155, 191, 48, 225, 201, 247, 191, 32, 79, 111, 33, 97, 206, 2, 50, 47, 207, 2, 17, 0, 0, 0, 5, 230, 210, 127, 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