Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea3cbb9e6af0a5669e613b2961d7d90ec4b1e646c89286072b3c677b316017d3

Tx prefix hash: bc3672cce64923de4a015c3023589f54e9fe1216012ce61af41d9ac2085b02bb
Tx public key: 2d790e40f5e1b29b0d4350de9344aaf9ba0a9b80504a6429c1f4d7290afe6fa2
Timestamp: 1741847552 Timestamp [UCT]: 2025-03-13 06:32:32 Age [y:d:h:m:s]: 00:269:17:00:34
Block: 1238230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190514 RingCT/type: yes/0
Extra: 012d790e40f5e1b29b0d4350de9344aaf9ba0a9b80504a6429c1f4d7290afe6fa2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43469eb18b8d4fedd50996d4c2180fb65badf8bc1153f5464b3552a4cd854eac 0.600000000000 1725189 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": 1238240, "vin": [ { "gen": { "height": 1238230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43469eb18b8d4fedd50996d4c2180fb65badf8bc1153f5464b3552a4cd854eac" } } ], "extra": [ 1, 45, 121, 14, 64, 245, 225, 178, 155, 13, 67, 80, 222, 147, 68, 170, 249, 186, 10, 155, 128, 80, 74, 100, 41, 193, 244, 215, 41, 10, 254, 111, 162, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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