Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdba127b4937c9ae5e96f7b71693fa88533bbd2cf5bea39d15a99662e860ea88

Tx prefix hash: 891b457f8444b4575021d277e94a39b04f483019eec1b912b41ad506844ba431
Tx public key: bcb47c27729ce2059e788b7f1245a2b457fb0aca4f7e95362f583dc219529ce5
Timestamp: 1720747152 Timestamp [UCT]: 2024-07-12 01:19:12 Age [y:d:h:m:s]: 00:271:10:21:24
Block: 1063755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193928 RingCT/type: yes/0
Extra: 01bcb47c27729ce2059e788b7f1245a2b457fb0aca4f7e95362f583dc219529ce502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 234ee84c07e4b83aff2ebc309ce4296f7062c781f2b3580d01646b07b457c431 0.600000000000 1534272 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": 1063765, "vin": [ { "gen": { "height": 1063755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "234ee84c07e4b83aff2ebc309ce4296f7062c781f2b3580d01646b07b457c431" } } ], "extra": [ 1, 188, 180, 124, 39, 114, 156, 226, 5, 158, 120, 139, 127, 18, 69, 162, 180, 87, 251, 10, 202, 79, 126, 149, 54, 47, 88, 61, 194, 25, 82, 156, 229, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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