Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c25dc309cc7534f7bae1941903fd8a90334a5e17048e1164073ea5c256c1a75

Tx prefix hash: ea37a51e242d949e91d3cfda51aa4a84fbe099e930a90ccd4c0773ce527d03fe
Tx public key: 5aeca4559631b05be3a16c0a450c6d621feae9e31fb75ace406d4f1370331883
Timestamp: 1736253270 Timestamp [UCT]: 2025-01-07 12:34:30 Age [y:d:h:m:s]: 00:086:13:41:53
Block: 1192166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61644 RingCT/type: yes/0
Extra: 015aeca4559631b05be3a16c0a450c6d621feae9e31fb75ace406d4f13703318830211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78e74844d2dec2ad9b1f01dd0b783c267d958d7098bb0e51fefafffc52f6322a 0.600000000000 1678715 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": 1192176, "vin": [ { "gen": { "height": 1192166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78e74844d2dec2ad9b1f01dd0b783c267d958d7098bb0e51fefafffc52f6322a" } } ], "extra": [ 1, 90, 236, 164, 85, 150, 49, 176, 91, 227, 161, 108, 10, 69, 12, 109, 98, 31, 234, 233, 227, 31, 183, 90, 206, 64, 109, 79, 19, 112, 51, 24, 131, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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