Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85ec8a4a49f0f22e6f25bd6f7b8fafeda5be76ed8694fedb3ebb3a9523a35003

Tx prefix hash: b18e3730a526bd9e7a3ca3a957608973584d445d52a85db3d261f1ed7dff1344
Tx public key: dc51404ddb44a1be1a7be9084bff03f582b1b1d12bae37a933e5eb6355534f3e
Timestamp: 1754460707 Timestamp [UCT]: 2025-08-06 06:11:47 Age [y:d:h:m:s]: 00:017:13:23:49
Block: 1341286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11617 RingCT/type: yes/0
Extra: 01dc51404ddb44a1be1a7be9084bff03f582b1b1d12bae37a933e5eb6355534f3e0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d95c3850382d3974862f8574b750cd537716cff964652e22f74081e60004a54 0.600000000000 1829109 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": 1341296, "vin": [ { "gen": { "height": 1341286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d95c3850382d3974862f8574b750cd537716cff964652e22f74081e60004a54" } } ], "extra": [ 1, 220, 81, 64, 77, 219, 68, 161, 190, 26, 123, 233, 8, 75, 255, 3, 245, 130, 177, 177, 209, 43, 174, 55, 169, 51, 229, 235, 99, 85, 83, 79, 62, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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