Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d37299f05605c6f50b899586757f840daa61bed4f9933cb52cf69974d09923db

Tx prefix hash: 713f10a654e077137b53e45fd3530bc22d5f5a54a2d1530b474b5944f44779c0
Tx public key: ffee42beaeab523652c93e5bea73f0b3a189862524d034dacef685550faf2d82
Timestamp: 1737909664 Timestamp [UCT]: 2025-01-26 16:41:04 Age [y:d:h:m:s]: 00:142:21:43:23
Block: 1205844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101857 RingCT/type: yes/0
Extra: 01ffee42beaeab523652c93e5bea73f0b3a189862524d034dacef685550faf2d82021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7ccd6d998a43a6c73c71a11a6648b8f87b6df69b0b428dd59ffb64c2e8a3baa 0.600000000000 1692543 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": 1205854, "vin": [ { "gen": { "height": 1205844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7ccd6d998a43a6c73c71a11a6648b8f87b6df69b0b428dd59ffb64c2e8a3baa" } } ], "extra": [ 1, 255, 238, 66, 190, 174, 171, 82, 54, 82, 201, 62, 91, 234, 115, 240, 179, 161, 137, 134, 37, 36, 208, 52, 218, 206, 246, 133, 85, 15, 175, 45, 130, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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