Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e482bbd1fd0940cba6f1a5f6ccbfb514223bb5d825c212baa9ec31a357c6f0f

Tx prefix hash: fecc61db0255085c5d50e2fc277941efb04da3d92e93f95c748df18374dafd7d
Tx public key: 14712938478a52df90ad3b13d0e45a985a1e830839a7c14eb2107ef586ff1554
Timestamp: 1674021203 Timestamp [UCT]: 2023-01-18 05:53:23 Age [y:d:h:m:s]: 01:301:22:33:54
Block: 677229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476770 RingCT/type: yes/0
Extra: 0114712938478a52df90ad3b13d0e45a985a1e830839a7c14eb2107ef586ff1554021100000003e6d27f9c000000000000000000

1 output(s) for total of 3.499928228000 dcy

stealth address amount amount idx
00: 9d57a56d59ae27f3075acd314290c31d7293f4a08e63f37f14cf535bac237509 3.499928228000 1118998 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": 677239, "vin": [ { "gen": { "height": 677229 } } ], "vout": [ { "amount": 3499928228, "target": { "key": "9d57a56d59ae27f3075acd314290c31d7293f4a08e63f37f14cf535bac237509" } } ], "extra": [ 1, 20, 113, 41, 56, 71, 138, 82, 223, 144, 173, 59, 19, 208, 228, 90, 152, 90, 30, 131, 8, 57, 167, 193, 78, 178, 16, 126, 245, 134, 255, 21, 84, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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