Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01b9b374476f48f0a90e8f1ce5aeb28acfe70ba45531e0323e0e6f678d868050

Tx prefix hash: 4ecbdbcdb159719b24e9505a2c487a4145f12f0a08ccd76206d6c9d0b7ded2d7
Tx public key: 983eac693f00a8f5e0da2e4bbec229ebc30cd5115fab533c95e53270fcacc119
Timestamp: 1716932101 Timestamp [UCT]: 2024-05-28 21:35:01 Age [y:d:h:m:s]: 00:334:15:14:19
Block: 1032135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239173 RingCT/type: yes/0
Extra: 01983eac693f00a8f5e0da2e4bbec229ebc30cd5115fab533c95e53270fcacc11902110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d19e805a3e7e0772896933f3dca900ef64c1bb2b14f607fd866a4cf9693a1609 0.600000000000 1500584 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": 1032145, "vin": [ { "gen": { "height": 1032135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d19e805a3e7e0772896933f3dca900ef64c1bb2b14f607fd866a4cf9693a1609" } } ], "extra": [ 1, 152, 62, 172, 105, 63, 0, 168, 245, 224, 218, 46, 75, 190, 194, 41, 235, 195, 12, 213, 17, 95, 171, 83, 60, 149, 229, 50, 112, 252, 172, 193, 25, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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