Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf1df6e8d29386b830836fe6af80a603365496ee8c2fcf2cfba461306cb36615

Tx prefix hash: f89c3076fc9faddfc3e849beddc422fac8af8afefa8d47e55a7c23fd8feb190e
Tx public key: 3ab3b57b49d78ddc88155b492edf57aa8e681ac19ffdbcbd959b77c43399f0e0
Timestamp: 1725127688 Timestamp [UCT]: 2024-08-31 18:08:08 Age [y:d:h:m:s]: 00:270:12:54:35
Block: 1100058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193269 RingCT/type: yes/0
Extra: 013ab3b57b49d78ddc88155b492edf57aa8e681ac19ffdbcbd959b77c43399f0e002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dddb8ada4b4a05baa269cb5697c034c45252414ca3d14eccbea6a3b48116e8f8 0.600000000000 1576031 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": 1100068, "vin": [ { "gen": { "height": 1100058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dddb8ada4b4a05baa269cb5697c034c45252414ca3d14eccbea6a3b48116e8f8" } } ], "extra": [ 1, 58, 179, 181, 123, 73, 215, 141, 220, 136, 21, 91, 73, 46, 223, 87, 170, 142, 104, 26, 193, 159, 253, 188, 189, 149, 155, 119, 196, 51, 153, 240, 224, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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