Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8774a727910085b11b33f54beb5e5bc62b5c0814b8d4a2ea4a91436b45a13dda

Tx prefix hash: 6e73e69cebfbbfd71a61a3aa415a3b4e1a140e4fb786f4fc7d381d49cd58021d
Tx public key: d73d4d3dd53d83d5e99234533ab74c285b096aa6f6da2545ca9180bc885aab28
Timestamp: 1705219995 Timestamp [UCT]: 2024-01-14 08:13:15 Age [y:d:h:m:s]: 01:065:02:31:12
Block: 935006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307644 RingCT/type: yes/0
Extra: 01d73d4d3dd53d83d5e99234533ab74c285b096aa6f6da2545ca9180bc885aab280211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0228268d5ea9289bb1e5bd8955d1fc8dd150966a9ec1fd13637c4520f3721dd 0.600000000000 1393022 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": 935016, "vin": [ { "gen": { "height": 935006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0228268d5ea9289bb1e5bd8955d1fc8dd150966a9ec1fd13637c4520f3721dd" } } ], "extra": [ 1, 215, 61, 77, 61, 213, 61, 131, 213, 233, 146, 52, 83, 58, 183, 76, 40, 91, 9, 106, 166, 246, 218, 37, 69, 202, 145, 128, 188, 136, 90, 171, 40, 2, 17, 0, 0, 0, 2, 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