Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cbe940cc4da7e19aaf5380fb6d95a2beceeb84e6c36d476885dc44dcc4e956d

Tx prefix hash: 43525f35e4b6ab8bacba3b2d39162f9f624c6433c8751410bcc6fdc14fc3d34b
Tx public key: 031638d323f00e19665484eb6a0862cbd27a9b9836f00cf4d3229ab4ff95712c
Timestamp: 1733263639 Timestamp [UCT]: 2024-12-03 22:07:19 Age [y:d:h:m:s]: 00:024:12:36:36
Block: 1167414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17545 RingCT/type: yes/0
Extra: 01031638d323f00e19665484eb6a0862cbd27a9b9836f00cf4d3229ab4ff95712c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee46d61d8fb187bc022738ee351563703395f837e7d8af46da659a4f425b4cf4 0.600000000000 1653109 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": 1167424, "vin": [ { "gen": { "height": 1167414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee46d61d8fb187bc022738ee351563703395f837e7d8af46da659a4f425b4cf4" } } ], "extra": [ 1, 3, 22, 56, 211, 35, 240, 14, 25, 102, 84, 132, 235, 106, 8, 98, 203, 210, 122, 155, 152, 54, 240, 12, 244, 211, 34, 154, 180, 255, 149, 113, 44, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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