Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8fff7fd95a3cfc8c0e0972ea770a39e3fce9f85933b57cf38b43ab36c5a54b5

Tx prefix hash: ca6b27b6e1fd3d8a52d411158c3e53c7405758261ec759625481173a99244986
Tx public key: 8c8b1e3eb69040139241b720f61383d27b81b7513e6250a88686b34fa323c1db
Timestamp: 1711464079 Timestamp [UCT]: 2024-03-26 14:41:19 Age [y:d:h:m:s]: 00:290:05:09:32
Block: 986812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207718 RingCT/type: yes/0
Extra: 018c8b1e3eb69040139241b720f61383d27b81b7513e6250a88686b34fa323c1db0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cbd77ab5d5cfe0c885b0b3546cc5007733665a90f072cc7187a818c36b31647 0.600000000000 1447047 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": 986822, "vin": [ { "gen": { "height": 986812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cbd77ab5d5cfe0c885b0b3546cc5007733665a90f072cc7187a818c36b31647" } } ], "extra": [ 1, 140, 139, 30, 62, 182, 144, 64, 19, 146, 65, 183, 32, 246, 19, 131, 210, 123, 129, 183, 81, 62, 98, 80, 168, 134, 134, 179, 79, 163, 35, 193, 219, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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