Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b021acee425553a19d827384329890822998ebb6abb3421d21dc80e0d4189cb9

Tx prefix hash: 30fd50f1874fa43e32c03c64b11a5c204c126dc43f2a5d691c586049f698d881
Tx public key: b00de5bf32a8543dd3f77e64b888e4bb67757befda5286620b0a13c95b4fd6f8
Timestamp: 1745727765 Timestamp [UCT]: 2025-04-27 04:22:45 Age [y:d:h:m:s]: 00:014:21:32:56
Block: 1270343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10649 RingCT/type: yes/0
Extra: 01b00de5bf32a8543dd3f77e64b888e4bb67757befda5286620b0a13c95b4fd6f8021100000006f7011ad5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fec8ae264e58f6858e6afdc1e5bcac1c3f2e4f33371f59ece9e6b023bd2e3e2 0.600000000000 1757586 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": 1270353, "vin": [ { "gen": { "height": 1270343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fec8ae264e58f6858e6afdc1e5bcac1c3f2e4f33371f59ece9e6b023bd2e3e2" } } ], "extra": [ 1, 176, 13, 229, 191, 50, 168, 84, 61, 211, 247, 126, 100, 184, 136, 228, 187, 103, 117, 123, 239, 218, 82, 134, 98, 11, 10, 19, 201, 91, 79, 214, 248, 2, 17, 0, 0, 0, 6, 247, 1, 26, 213, 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