Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f72d22c8fc7193b5c4d9edc4f7a61591b5556983e1b6ed4b63e98afac820526e

Tx prefix hash: cd8434cfb8e5cee5ef9eaa2b527e680bff0ccdb61d99e78100b788e6b30652b2
Tx public key: 47c2973ec421e7f2e44c92acffc408222e1083ed720c1e336d2ba4b6c2c0df4e
Timestamp: 1706388409 Timestamp [UCT]: 2024-01-27 20:46:49 Age [y:d:h:m:s]: 00:301:10:10:50
Block: 944677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215841 RingCT/type: yes/0
Extra: 0147c2973ec421e7f2e44c92acffc408222e1083ed720c1e336d2ba4b6c2c0df4e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f1d18307b1ca9628e4bacb2b9edb44dcd0cad579788bb28e40fd292a1bcd2af 0.600000000000 1402963 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": 944687, "vin": [ { "gen": { "height": 944677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f1d18307b1ca9628e4bacb2b9edb44dcd0cad579788bb28e40fd292a1bcd2af" } } ], "extra": [ 1, 71, 194, 151, 62, 196, 33, 231, 242, 228, 76, 146, 172, 255, 196, 8, 34, 46, 16, 131, 237, 114, 12, 30, 51, 109, 43, 164, 182, 194, 192, 223, 78, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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