Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 961f650a569a31da4dcfbec7637aa87d67e654a2d4a4277fcd32dee7437053e0

Tx prefix hash: 639c53314959d30c22aad4e31732150f7b0278756ea6b9954f6a008e82fa63c4
Tx public key: d7f1b4c1f57006220284c6a0ea746ea999c3cb372a32951d1ceeacae65ce6409
Timestamp: 1701736916 Timestamp [UCT]: 2023-12-05 00:41:56 Age [y:d:h:m:s]: 01:159:20:01:03
Block: 906134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375419 RingCT/type: yes/0
Extra: 01d7f1b4c1f57006220284c6a0ea746ea999c3cb372a32951d1ceeacae65ce640902110000000275e3f0e9000000000000000000

1 output(s) for total of 0.610382226000 dcy

stealth address amount amount idx
00: d13ee52fd9d4715286f7aa1231d52057c9bb68dcf89c4bd7d1de70a15c8c7c67 0.610382226000 1363057 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": 906144, "vin": [ { "gen": { "height": 906134 } } ], "vout": [ { "amount": 610382226, "target": { "key": "d13ee52fd9d4715286f7aa1231d52057c9bb68dcf89c4bd7d1de70a15c8c7c67" } } ], "extra": [ 1, 215, 241, 180, 193, 245, 112, 6, 34, 2, 132, 198, 160, 234, 116, 110, 169, 153, 195, 203, 55, 42, 50, 149, 29, 28, 238, 172, 174, 101, 206, 100, 9, 2, 17, 0, 0, 0, 2, 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