Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 078816095a07161419f5cfff96d6e1f8b4fdf496e0eb52fe6acb21fb2d8d7769

Tx prefix hash: 625857f6ccd58b86a915cc9bb2133b4ceb0e5323d24dc3dad5bb0f40deb3dcd1
Tx public key: c790bae8db11554b5b309d5bd8fe9b22aa4d7075baa3c745a6b6888f96a7aaa1
Timestamp: 1663002217 Timestamp [UCT]: 2022-09-12 17:03:37 Age [y:d:h:m:s]: 03:050:02:24:38
Block: 586456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 815682 RingCT/type: yes/0
Extra: 01c790bae8db11554b5b309d5bd8fe9b22aa4d7075baa3c745a6b6888f96a7aaa102110000000275e3f0e9000000000000000000

1 output(s) for total of 6.995647234000 dcy

stealth address amount amount idx
00: 1d7c4bb622c6a25d0ff2112f1a015b217cf9bcc9821a97c569ad028526bc1bff 6.995647234000 1020565 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": 586466, "vin": [ { "gen": { "height": 586456 } } ], "vout": [ { "amount": 6995647234, "target": { "key": "1d7c4bb622c6a25d0ff2112f1a015b217cf9bcc9821a97c569ad028526bc1bff" } } ], "extra": [ 1, 199, 144, 186, 232, 219, 17, 85, 75, 91, 48, 157, 91, 216, 254, 155, 34, 170, 77, 112, 117, 186, 163, 199, 69, 166, 182, 136, 143, 150, 167, 170, 161, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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