Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bac62000b779d5bbbdca14d79b7765ed503893f1be5a944a05bacd7d42882b1d

Tx prefix hash: b0596c1a8fabfdb1d6b1dbd638c905ae42a912287a148a30ed1f94f6a7c1b83c
Tx public key: bf377fc3c2762025d6915fea81c8cb098ad84252d2cfd641ac6c4aa7f3c58d39
Timestamp: 1720245562 Timestamp [UCT]: 2024-07-06 05:59:22 Age [y:d:h:m:s]: 00:251:18:53:00
Block: 1059592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179899 RingCT/type: yes/0
Extra: 01bf377fc3c2762025d6915fea81c8cb098ad84252d2cfd641ac6c4aa7f3c58d3902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4cf72c515bd9aacec454b9e3eda6d62c68c0b9e53f7dadfd53ba28676514df4 0.600000000000 1530061 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": 1059602, "vin": [ { "gen": { "height": 1059592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4cf72c515bd9aacec454b9e3eda6d62c68c0b9e53f7dadfd53ba28676514df4" } } ], "extra": [ 1, 191, 55, 127, 195, 194, 118, 32, 37, 214, 145, 95, 234, 129, 200, 203, 9, 138, 216, 66, 82, 210, 207, 214, 65, 172, 108, 74, 167, 243, 197, 141, 57, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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