Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f489678c964f8fc68115d100bfaf19cd3676396a5970ae0e45a7a95af546f73c

Tx prefix hash: f4d9db1f7ebdabcc3ec77bea9911cc3e829160a7eab5a30c08cc397491b57ce3
Tx public key: 47e81ae1236910c7062646d3164e4224445130f041f105d5ece35bfe03aed667
Timestamp: 1578828973 Timestamp [UCT]: 2020-01-12 11:36:13 Age [y:d:h:m:s]: 05:061:22:32:33
Block: 43903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1194429 RingCT/type: yes/0
Extra: 0147e81ae1236910c7062646d3164e4224445130f041f105d5ece35bfe03aed66702110000000b4ac5aa02000000000000000000

1 output(s) for total of 439.068193861000 dcy

stealth address amount amount idx
00: 758ef948e5f9f4a7fa5409e4f6aeda9c9894f5e24fce45b4764a7f15e36f904d 439.068193861000 79693 of 0

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": 43913, "vin": [ { "gen": { "height": 43903 } } ], "vout": [ { "amount": 439068193861, "target": { "key": "758ef948e5f9f4a7fa5409e4f6aeda9c9894f5e24fce45b4764a7f15e36f904d" } } ], "extra": [ 1, 71, 232, 26, 225, 35, 105, 16, 199, 6, 38, 70, 211, 22, 78, 66, 36, 68, 81, 48, 240, 65, 241, 5, 213, 236, 227, 91, 254, 3, 174, 214, 103, 2, 17, 0, 0, 0, 11, 74, 197, 170, 2, 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