Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 839258ed4f3d6141f72a73ae4612105a616b9c3ac521b302e4b4c1a33c6a0dcb

Tx prefix hash: c25d7ec2021b1097edff2bc45ffe2dcf775b2ccd6e84f00606dedca0ab33671a
Tx public key: 27153ce4d4a7c0728101945340318ae2abe6e565365b86b3984e70a0f7f874c5
Timestamp: 1719757287 Timestamp [UCT]: 2024-06-30 14:21:27 Age [y:d:h:m:s]: 00:271:07:06:53
Block: 1055533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193848 RingCT/type: yes/0
Extra: 0127153ce4d4a7c0728101945340318ae2abe6e565365b86b3984e70a0f7f874c50211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 815ca425987e75be6999337096c14ec9c4d725d9ecfa34eb0c4c1e746c01d66b 0.600000000000 1525938 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": 1055543, "vin": [ { "gen": { "height": 1055533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "815ca425987e75be6999337096c14ec9c4d725d9ecfa34eb0c4c1e746c01d66b" } } ], "extra": [ 1, 39, 21, 60, 228, 212, 167, 192, 114, 129, 1, 148, 83, 64, 49, 138, 226, 171, 230, 229, 101, 54, 91, 134, 179, 152, 78, 112, 160, 247, 248, 116, 197, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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