Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f1a06849f2f2d436817adf62c9852c612443d5c752605162171bbf15c22e991

Tx prefix hash: 730107795dc203d2cb6483f541f96f36de99cb8049e0aa4ae4003f618a52619a
Tx public key: f178e52ce81fcf679e23073346c3f56204409cb1c2081eccff1fdabcc8420b47
Timestamp: 1629027444 Timestamp [UCT]: 2021-08-15 11:37:24 Age [y:d:h:m:s]: 03:201:13:48:14
Block: 314578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 917037 RingCT/type: yes/0
Extra: 01f178e52ce81fcf679e23073346c3f56204409cb1c2081eccff1fdabcc8420b4702110000004701f1e57f000000000000000000

1 output(s) for total of 55.677603488000 dcy

stealth address amount amount idx
00: 692c33b07c825f0efba4d7fea678b2334b264052c167ddb9e77fd65c608dcc22 55.677603488000 654833 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": 314588, "vin": [ { "gen": { "height": 314578 } } ], "vout": [ { "amount": 55677603488, "target": { "key": "692c33b07c825f0efba4d7fea678b2334b264052c167ddb9e77fd65c608dcc22" } } ], "extra": [ 1, 241, 120, 229, 44, 232, 31, 207, 103, 158, 35, 7, 51, 70, 195, 245, 98, 4, 64, 156, 177, 194, 8, 30, 204, 255, 31, 218, 188, 200, 66, 11, 71, 2, 17, 0, 0, 0, 71, 1, 241, 229, 127, 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