Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 031863c66b510d94e51a2f62308ab94675edde6837e9a7436e616560c6da321b

Tx prefix hash: 73746b7ce97267380868eae3f02c0dd326bca76f35fd51704a90c6be4f505023
Tx public key: 1bac5675962bb83a0dd3a45cb59d67ebf8cbb1d4d80467ec40556f5af08a9eee
Timestamp: 1698333885 Timestamp [UCT]: 2023-10-26 15:24:45 Age [y:d:h:m:s]: 01:087:10:02:20
Block: 878153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323654 RingCT/type: yes/0
Extra: 011bac5675962bb83a0dd3a45cb59d67ebf8cbb1d4d80467ec40556f5af08a9eee02110000000733af99f4000000000000000000

1 output(s) for total of 0.755639388000 dcy

stealth address amount amount idx
00: faed2affa006cd38c3f7ede611a496cfecf598d3beb8aa15e9a9657782e3ab91 0.755639388000 1333569 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": 878163, "vin": [ { "gen": { "height": 878153 } } ], "vout": [ { "amount": 755639388, "target": { "key": "faed2affa006cd38c3f7ede611a496cfecf598d3beb8aa15e9a9657782e3ab91" } } ], "extra": [ 1, 27, 172, 86, 117, 150, 43, 184, 58, 13, 211, 164, 92, 181, 157, 103, 235, 248, 203, 177, 212, 216, 4, 103, 236, 64, 85, 111, 90, 240, 138, 158, 238, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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