Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bafd286fdbfecc2050c91b5c87baa89fb6970e328b3e167a07de4e61c14bd18a

Tx prefix hash: 1263b4c3a86faca58cd3b456d8d796cce641e5d2abbc50dd4f59e43a54684c74
Tx public key: e4ab3221fea71ce99c01858af3a711a8e9e10e63b6cd567eb04c005dd14d828a
Timestamp: 1685059156 Timestamp [UCT]: 2023-05-25 23:59:16 Age [y:d:h:m:s]: 01:355:12:26:17
Block: 768127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515327 RingCT/type: yes/0
Extra: 01e4ab3221fea71ce99c01858af3a711a8e9e10e63b6cd567eb04c005dd14d828a02110000000333af99f4000000000000000000

1 output(s) for total of 1.749349402000 dcy

stealth address amount amount idx
00: f64febfdec86c521a8ef9a07529b1f452495d946a535482f20aa9b1502f02f3b 1.749349402000 1217314 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": 768137, "vin": [ { "gen": { "height": 768127 } } ], "vout": [ { "amount": 1749349402, "target": { "key": "f64febfdec86c521a8ef9a07529b1f452495d946a535482f20aa9b1502f02f3b" } } ], "extra": [ 1, 228, 171, 50, 33, 254, 167, 28, 233, 156, 1, 133, 138, 243, 167, 17, 168, 233, 225, 14, 99, 182, 205, 86, 126, 176, 76, 0, 93, 209, 77, 130, 138, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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