Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fe9486bd34fda0cbe128a6c811e5e34d5d07140a7f0b25ad31229d001f27ba7

Tx prefix hash: c3fc5057a673a9000e0669cd8d313eb44527b709081fa69a258e8e1b72b7eab4
Tx public key: c45d4014e5bb9fb3ef6555939e74322a77f2f56c7c5b7b355798486a0fa84a78
Timestamp: 1715131679 Timestamp [UCT]: 2024-05-08 01:27:59 Age [y:d:h:m:s]: 00:293:08:34:23
Block: 1017191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209670 RingCT/type: yes/0
Extra: 01c45d4014e5bb9fb3ef6555939e74322a77f2f56c7c5b7b355798486a0fa84a780211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3be7d78fb57e7cb44815c7214d9a73d5064e542772cb371ee908f14fb95c2773 0.600000000000 1480958 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": 1017201, "vin": [ { "gen": { "height": 1017191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3be7d78fb57e7cb44815c7214d9a73d5064e542772cb371ee908f14fb95c2773" } } ], "extra": [ 1, 196, 93, 64, 20, 229, 187, 159, 179, 239, 101, 85, 147, 158, 116, 50, 42, 119, 242, 245, 108, 124, 91, 123, 53, 87, 152, 72, 106, 15, 168, 74, 120, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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