Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55309e9375d87530ef63f013ecf9deab69bda95daa9e84130ed126816145f753

Tx prefix hash: 371e22959adc5ea1f7e6bccd2363ec2e9662d2287fdd3bc9aa78e4f7c42db65c
Tx public key: 26820c7866c893336e90d4334837123d65439c362aefe89f24fa8d4179d6f2cf
Timestamp: 1704555354 Timestamp [UCT]: 2024-01-06 15:35:54 Age [y:d:h:m:s]: 01:095:12:12:12
Block: 929501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329373 RingCT/type: yes/0
Extra: 0126820c7866c893336e90d4334837123d65439c362aefe89f24fa8d4179d6f2cf0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4673647aee84314b887dbf2d65a623f8a5a0f60d12da4c1b1eb6ce6da07efa2a 0.600000000000 1387377 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": 929511, "vin": [ { "gen": { "height": 929501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4673647aee84314b887dbf2d65a623f8a5a0f60d12da4c1b1eb6ce6da07efa2a" } } ], "extra": [ 1, 38, 130, 12, 120, 102, 200, 147, 51, 110, 144, 212, 51, 72, 55, 18, 61, 101, 67, 156, 54, 42, 239, 232, 159, 36, 250, 141, 65, 121, 214, 242, 207, 2, 17, 0, 0, 0, 2, 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