Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1091fd6b57c87e9932f4216df0bd2307e219a61aebd2adb0860e95ae97b8ed29

Tx prefix hash: 01c5bd14bf2df32a59cbfaeb8dd3470f63439a5091983a57a2ce716d9e2b40a0
Tx public key: 5719c27643d343609289365e67223501f2e25c8c30ef6453cd9292ee68a8f523
Timestamp: 1709222070 Timestamp [UCT]: 2024-02-29 15:54:30 Age [y:d:h:m:s]: 01:251:16:23:32
Block: 968205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438603 RingCT/type: yes/0
Extra: 015719c27643d343609289365e67223501f2e25c8c30ef6453cd9292ee68a8f52302110000000d52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34ba8d46d55b7b47187a14eb3d2d6d41c79c577797904cb80b34c8fe7fd8a67a 0.600000000000 1428006 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": 968215, "vin": [ { "gen": { "height": 968205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34ba8d46d55b7b47187a14eb3d2d6d41c79c577797904cb80b34c8fe7fd8a67a" } } ], "extra": [ 1, 87, 25, 194, 118, 67, 211, 67, 96, 146, 137, 54, 94, 103, 34, 53, 1, 242, 226, 92, 140, 48, 239, 100, 83, 205, 146, 146, 238, 104, 168, 245, 35, 2, 17, 0, 0, 0, 13, 82, 212, 126, 148, 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