Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86eda59172a450a091e5d802003fba491afbfc8dc615c8398494fb9071935d72

Tx prefix hash: 33671660b9b280b789105c74f7e8c214a6ec10b91df42bcd5433f1d9b479c911
Tx public key: 2c1264f82018004555ef833077f93073efbf4fdc6addc708f1413e6aa65d760d
Timestamp: 1687980112 Timestamp [UCT]: 2023-06-28 19:21:52 Age [y:d:h:m:s]: 01:323:10:08:43
Block: 792358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492314 RingCT/type: yes/0
Extra: 012c1264f82018004555ef833077f93073efbf4fdc6addc708f1413e6aa65d760d02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.454082888000 dcy

stealth address amount amount idx
00: c0da7afbe7cc4f35405bf74ff5ed7c4c4a9a1f1743c23e9dabba23753ddec53f 1.454082888000 1242951 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": 792368, "vin": [ { "gen": { "height": 792358 } } ], "vout": [ { "amount": 1454082888, "target": { "key": "c0da7afbe7cc4f35405bf74ff5ed7c4c4a9a1f1743c23e9dabba23753ddec53f" } } ], "extra": [ 1, 44, 18, 100, 248, 32, 24, 0, 69, 85, 239, 131, 48, 119, 249, 48, 115, 239, 191, 79, 220, 106, 221, 199, 8, 241, 65, 62, 106, 166, 93, 118, 13, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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