Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91e760ef46d557d7ab68b4f3beb23ddcbd499296af73213d369f6ffa67acea19

Tx prefix hash: b33a4bae672d11a43d0e7d090019ca93262ec09fea59184afd568151577521a9
Tx public key: f50c429c8a8ea40aa17e975f1244e8a0e32ba1da08dc313fe39e005392aed3ee
Timestamp: 1757273403 Timestamp [UCT]: 2025-09-07 19:30:03 Age [y:d:h:m:s]: 00:142:01:48:38
Block: 1363556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101460 RingCT/type: yes/0
Extra: 01f50c429c8a8ea40aa17e975f1244e8a0e32ba1da08dc313fe39e005392aed3ee021100000001b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 468b703dd9a0b6869dec3ae79026817e973ecb0b3d160590b20ee64bec13c8cb 0.600000000000 1851595 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": 1363566, "vin": [ { "gen": { "height": 1363556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "468b703dd9a0b6869dec3ae79026817e973ecb0b3d160590b20ee64bec13c8cb" } } ], "extra": [ 1, 245, 12, 66, 156, 138, 142, 164, 10, 161, 126, 151, 95, 18, 68, 232, 160, 227, 43, 161, 218, 8, 220, 49, 63, 227, 158, 0, 83, 146, 174, 211, 238, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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