Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42fa0db07dbfc3c707bc6ff9043ab19667b57810cfa9a2cd936391fbecacad84

Tx prefix hash: 09305c94dc1b0523ce494b7ca212573fc61fe9b6cf1e5d37f165b6ed0ba0fb34
Tx public key: 34f1de6cebe82197e6cd8bc676608094480d659e18d4c2c9c2ba457b14bd0f90
Timestamp: 1712446547 Timestamp [UCT]: 2024-04-06 23:35:47 Age [y:d:h:m:s]: 00:220:11:31:21
Block: 994901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157873 RingCT/type: yes/0
Extra: 0134f1de6cebe82197e6cd8bc676608094480d659e18d4c2c9c2ba457b14bd0f9002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef01ea4de765d3c6d3ef3da7b642fea8cfb2a9a3926eaae1d483f900f23d0a39 0.600000000000 1455305 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": 994911, "vin": [ { "gen": { "height": 994901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef01ea4de765d3c6d3ef3da7b642fea8cfb2a9a3926eaae1d483f900f23d0a39" } } ], "extra": [ 1, 52, 241, 222, 108, 235, 232, 33, 151, 230, 205, 139, 198, 118, 96, 128, 148, 72, 13, 101, 158, 24, 212, 194, 201, 194, 186, 69, 123, 20, 189, 15, 144, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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