Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20c74f12880d3fb6643fca03dc1441cdc0799d5bbc2150d656b34994a1badaee

Tx prefix hash: dea960f3184d7afabc7c25d556bc07b82beeb494d7edf7db2fb1a54992d4f03b
Tx public key: f735090a101b3280f9c4a78f2dcea6a88ae50406c59948fb5853f5a57a97b1df
Timestamp: 1762884726 Timestamp [UCT]: 2025-11-11 18:12:06 Age [y:d:h:m:s]: 00:009:20:52:37
Block: 1409967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7053 RingCT/type: yes/0
Extra: 01f735090a101b3280f9c4a78f2dcea6a88ae50406c59948fb5853f5a57a97b1df02110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65aca49ddb90f77c884de94b32f8e19b7c74e7cfe7a3ff129ce7a935c3e7d851 0.600000000000 1898416 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": 1409977, "vin": [ { "gen": { "height": 1409967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65aca49ddb90f77c884de94b32f8e19b7c74e7cfe7a3ff129ce7a935c3e7d851" } } ], "extra": [ 1, 247, 53, 9, 10, 16, 27, 50, 128, 249, 196, 167, 143, 45, 206, 166, 168, 138, 229, 4, 6, 197, 153, 72, 251, 88, 83, 245, 165, 122, 151, 177, 223, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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