Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0e6d6cba51a484e9f56c920f70e82a0f8915400257588d69f59760b87088780

Tx prefix hash: c8f08c83d8f2db31f9b4922e41a0e5e8b3f078ddcf78785ea0656707f70687e4
Tx public key: 7cea0da6622e01ca6b5eb3ee1fab1573b809750122f88cfc81f76cf0dbd91363
Timestamp: 1723061262 Timestamp [UCT]: 2024-08-07 20:07:42 Age [y:d:h:m:s]: 00:238:12:50:07
Block: 1082932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170364 RingCT/type: yes/0
Extra: 017cea0da6622e01ca6b5eb3ee1fab1573b809750122f88cfc81f76cf0dbd91363021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 801ba7412fa2b98b7d2315b7d2b3be1aaf0e3194c6b58c768e78c63db26f927b 0.600000000000 1556767 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": 1082942, "vin": [ { "gen": { "height": 1082932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "801ba7412fa2b98b7d2315b7d2b3be1aaf0e3194c6b58c768e78c63db26f927b" } } ], "extra": [ 1, 124, 234, 13, 166, 98, 46, 1, 202, 107, 94, 179, 238, 31, 171, 21, 115, 184, 9, 117, 1, 34, 248, 140, 252, 129, 247, 108, 240, 219, 217, 19, 99, 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