Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf030baecf75a715e85aa98e8cda2d029fcffa1c81c586576df87e5edb120a8b

Tx prefix hash: 04de4237d7872a7236c91cb5ac386cd899a389df406d2bccdaac423b9491db4f
Tx public key: 5a90e6502cbea91431c7276febbf7640578e2b957a8b6e8df977f084c7333162
Timestamp: 1749301304 Timestamp [UCT]: 2025-06-07 13:01:44 Age [y:d:h:m:s]: 00:161:04:51:36
Block: 1299934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112879 RingCT/type: yes/0
Extra: 015a90e6502cbea91431c7276febbf7640578e2b957a8b6e8df977f084c7333162021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7f675ad67fccf99b959e8362dced4909f513dc3653d02ef0ed0b16ab9b0c8ac 0.600000000000 1787477 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": 1299944, "vin": [ { "gen": { "height": 1299934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7f675ad67fccf99b959e8362dced4909f513dc3653d02ef0ed0b16ab9b0c8ac" } } ], "extra": [ 1, 90, 144, 230, 80, 44, 190, 169, 20, 49, 199, 39, 111, 235, 191, 118, 64, 87, 142, 43, 149, 122, 139, 110, 141, 249, 119, 240, 132, 199, 51, 49, 98, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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