Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3ee145245354505e2eba1ba0df4a153279df321c970027e72b7c69011ffbfbb

Tx prefix hash: 0bcc8867f04a21cd55eecb5ca43ad5d0bb440fa5d8207fc325af31eab2bc2751
Tx public key: f0692e85c03239f1bd49412b0da4ff0c8ceccaa734787020a9090ebe7fb04aa3
Timestamp: 1632272525 Timestamp [UCT]: 2021-09-22 01:02:05 Age [y:d:h:m:s]: 03:200:21:36:08
Block: 338453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 919548 RingCT/type: yes/0
Extra: 01f0692e85c03239f1bd49412b0da4ff0c8ceccaa734787020a9090ebe7fb04aa3021100000073f29d7abf000000000000000000

1 output(s) for total of 46.405839522000 dcy

stealth address amount amount idx
00: f4cf9c6ee83b53e797789eb16fc5f9c8ae3541ca680915294a691a52fa90fb49 46.405839522000 696554 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": 338463, "vin": [ { "gen": { "height": 338453 } } ], "vout": [ { "amount": 46405839522, "target": { "key": "f4cf9c6ee83b53e797789eb16fc5f9c8ae3541ca680915294a691a52fa90fb49" } } ], "extra": [ 1, 240, 105, 46, 133, 192, 50, 57, 241, 189, 73, 65, 43, 13, 164, 255, 12, 140, 236, 202, 167, 52, 120, 112, 32, 169, 9, 14, 190, 127, 176, 74, 163, 2, 17, 0, 0, 0, 115, 242, 157, 122, 191, 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