Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ddf21930137d1f218c1a67e4de80cb25c47dc1bcfa4ec86c14e2620827f7b74

Tx prefix hash: f6a2fa0150beff7fb836bdef8deda30ebee4cf8cb2fc6c68b7e9d9ee3ce4d1ad
Tx public key: 74504e928bc5330634ca5a3db8a690250b2c76bbbbbc422c7374ce4e5e63c935
Timestamp: 1764602019 Timestamp [UCT]: 2025-12-01 15:13:39 Age [y:d:h:m:s]: 00:059:18:34:27
Block: 1424199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42618 RingCT/type: yes/0
Extra: 0174504e928bc5330634ca5a3db8a690250b2c76bbbbbc422c7374ce4e5e63c935021100000001fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05fd4ba6444295e46c88efa51a3f0a061369774b5277fd7a76f13c258589c1d3 0.600000000000 1912830 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": 1424209, "vin": [ { "gen": { "height": 1424199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05fd4ba6444295e46c88efa51a3f0a061369774b5277fd7a76f13c258589c1d3" } } ], "extra": [ 1, 116, 80, 78, 146, 139, 197, 51, 6, 52, 202, 90, 61, 184, 166, 144, 37, 11, 44, 118, 187, 187, 188, 66, 44, 115, 116, 206, 78, 94, 99, 201, 53, 2, 17, 0, 0, 0, 1, 251, 143, 208, 137, 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