Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4358e02a3c06b0c1bc785c3188933ed3cc61b4304dce9ce3e51a7fd4b710751

Tx prefix hash: 8330c5a037891f347741a60e60c8fadf93569b86704d4d5fb1a3551a895e01be
Tx public key: fbb09fc441669f570902a98c898b3f396e27a1d8f56b4f88157009ddb03a51cb
Timestamp: 1702139091 Timestamp [UCT]: 2023-12-09 16:24:51 Age [y:d:h:m:s]: 01:167:12:22:06
Block: 909483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380903 RingCT/type: yes/0
Extra: 01fbb09fc441669f570902a98c898b3f396e27a1d8f56b4f88157009ddb03a51cb021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fe900e7084cf687a95bd7b51b4a07fc5388075a4082e30d281642e748c37d02 0.600000000000 1366574 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": 909493, "vin": [ { "gen": { "height": 909483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fe900e7084cf687a95bd7b51b4a07fc5388075a4082e30d281642e748c37d02" } } ], "extra": [ 1, 251, 176, 159, 196, 65, 102, 159, 87, 9, 2, 169, 140, 137, 139, 63, 57, 110, 39, 161, 216, 245, 107, 79, 136, 21, 112, 9, 221, 176, 58, 81, 203, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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