Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c71e77ba39b2ad7da0c2dc4914dc2846ce625c7965270b2383f8e6010590f7e5

Tx prefix hash: 884d50fda930d26e37d138e8528c6ebdb2cbac83e696c2e58835f8988ce4a071
Tx public key: b6de288ec324cde49cc36890741cfdd0bd44a95475bb2f2c5a4dae868d3238d3
Timestamp: 1701210350 Timestamp [UCT]: 2023-11-28 22:25:50 Age [y:d:h:m:s]: 01:161:05:50:48
Block: 901783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376411 RingCT/type: yes/0
Extra: 01b6de288ec324cde49cc36890741cfdd0bd44a95475bb2f2c5a4dae868d3238d302110000000633af99f4000000000000000000

1 output(s) for total of 0.630984301000 dcy

stealth address amount amount idx
00: a771a6efe52fa1778348be1562137b924113add443451eca39f36cd5ea8ca81e 0.630984301000 1358374 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": 901793, "vin": [ { "gen": { "height": 901783 } } ], "vout": [ { "amount": 630984301, "target": { "key": "a771a6efe52fa1778348be1562137b924113add443451eca39f36cd5ea8ca81e" } } ], "extra": [ 1, 182, 222, 40, 142, 195, 36, 205, 228, 156, 195, 104, 144, 116, 28, 253, 208, 189, 68, 169, 84, 117, 187, 47, 44, 90, 77, 174, 134, 141, 50, 56, 211, 2, 17, 0, 0, 0, 6, 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