Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b48edcfba9e19ceb4be88ab0ac51d6c4a741a2e311babc9e200c66c5543f77f

Tx prefix hash: e276bfe1f33c2444f0278d1f09b2b14838ce423f62592f658a88a7a693d23d19
Tx public key: d7fe1e7436defb0dbe391ced2a31e1c16b8522bed1afdace21ca73623801a3c2
Timestamp: 1765225541 Timestamp [UCT]: 2025-12-08 20:25:41 Age [y:d:h:m:s]: 00:054:14:47:16
Block: 1429364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 38923 RingCT/type: yes/0
Extra: 01d7fe1e7436defb0dbe391ced2a31e1c16b8522bed1afdace21ca73623801a3c202090000000bd48050ef00

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2d47c01b3d3a91f4c3d9e8bb05dd2dd1b4ad6baade04121e86c36932cdfa7d1 0.600000000000 1918089 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": 1429374, "vin": [ { "gen": { "height": 1429364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2d47c01b3d3a91f4c3d9e8bb05dd2dd1b4ad6baade04121e86c36932cdfa7d1" } } ], "extra": [ 1, 215, 254, 30, 116, 54, 222, 251, 13, 190, 57, 28, 237, 42, 49, 225, 193, 107, 133, 34, 190, 209, 175, 218, 206, 33, 202, 115, 98, 56, 1, 163, 194, 2, 9, 0, 0, 0, 11, 212, 128, 80, 239, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8