Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e389b2a230e1ddef6ce37086c381b9ca85dd0dcffb576b9234735ba04a602d1

Tx prefix hash: 77fb5d480e5891d4c43d5c277b868c1ceb7e1415ccafc1516f5917c3068fc242
Tx public key: b8d6d10ef67a9b208d27cdb36815cb1b408585c9d6db8855f10288ed912dd3bc
Timestamp: 1712331610 Timestamp [UCT]: 2024-04-05 15:40:10 Age [y:d:h:m:s]: 00:223:03:20:20
Block: 993955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159769 RingCT/type: yes/0
Extra: 01b8d6d10ef67a9b208d27cdb36815cb1b408585c9d6db8855f10288ed912dd3bc02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc8699880e956f5195b142899f826dceda3c727d5920a2e349dc2a3cb18070a6 0.600000000000 1454351 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": 993965, "vin": [ { "gen": { "height": 993955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc8699880e956f5195b142899f826dceda3c727d5920a2e349dc2a3cb18070a6" } } ], "extra": [ 1, 184, 214, 209, 14, 246, 122, 155, 32, 141, 39, 205, 179, 104, 21, 203, 27, 64, 133, 133, 201, 214, 219, 136, 85, 241, 2, 136, 237, 145, 45, 211, 188, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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