Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c50efef9266f093670985abdae6945df9da833fa282e37732258e0c5f3111304

Tx prefix hash: bb5431869d452c4b7970f38592994bf2866ad59ac9bb0c8c3ac8651629aadb4c
Tx public key: 6a8a362f1aa7cfcb5ac217ce8b1b7cbec042107981f24b9c851440c186462c54
Timestamp: 1736508709 Timestamp [UCT]: 2025-01-10 11:31:49 Age [y:d:h:m:s]: 00:076:12:26:16
Block: 1194271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54464 RingCT/type: yes/0
Extra: 016a8a362f1aa7cfcb5ac217ce8b1b7cbec042107981f24b9c851440c186462c540211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a587a72fe9ff8eeae2a2896d4f81698d7692d437517191732f3db1b5d56b793 0.600000000000 1680840 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": 1194281, "vin": [ { "gen": { "height": 1194271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a587a72fe9ff8eeae2a2896d4f81698d7692d437517191732f3db1b5d56b793" } } ], "extra": [ 1, 106, 138, 54, 47, 26, 167, 207, 203, 90, 194, 23, 206, 139, 27, 124, 190, 192, 66, 16, 121, 129, 242, 75, 156, 133, 20, 64, 193, 134, 70, 44, 84, 2, 17, 0, 0, 0, 4, 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