Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1531db09ad56d5293fb10c4ec6365b5acc9d4f95f5392fff5190817f485b44f

Tx prefix hash: 2e786536b19142b67a53f4b4c9cd39c79604a62dad6126bd48f03e52c72764f7
Tx public key: 19047521318502e92d7a5fd2694f1d3af57f50c5cd9cf60c9a11f08aa95086fd
Timestamp: 1740008985 Timestamp [UCT]: 2025-02-19 23:49:45 Age [y:d:h:m:s]: 00:230:07:57:34
Block: 1222963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162340 RingCT/type: yes/0
Extra: 0119047521318502e92d7a5fd2694f1d3af57f50c5cd9cf60c9a11f08aa95086fd021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb30a55c3b80e7c6af63f82ba4ccf3f5ca2dce18adb86dd4086fa8fe49ecc0d2 0.600000000000 1709818 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": 1222973, "vin": [ { "gen": { "height": 1222963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb30a55c3b80e7c6af63f82ba4ccf3f5ca2dce18adb86dd4086fa8fe49ecc0d2" } } ], "extra": [ 1, 25, 4, 117, 33, 49, 133, 2, 233, 45, 122, 95, 210, 105, 79, 29, 58, 245, 127, 80, 197, 205, 156, 246, 12, 154, 17, 240, 138, 169, 80, 134, 253, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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