Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 344dfa2d215d210e2f103296f28e15123179ef3890e390fcda9fde3ff2ba8660

Tx prefix hash: 1f21fe2468e5e7a431a7c0d91820a94ae230a43a9d6428be972ee88d250b66eb
Tx public key: 22ed496b943e224ed1aa585eebe63ac23d738dd9107f37f56c8144eaf08c205f
Timestamp: 1583063244 Timestamp [UCT]: 2020-03-01 11:47:24 Age [y:d:h:m:s]: 04:301:10:08:43
Block: 74457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1109401 RingCT/type: yes/0
Extra: 0122ed496b943e224ed1aa585eebe63ac23d738dd9107f37f56c8144eaf08c205f021100000233026b59f3000000000000000000

1 output(s) for total of 347.771387861000 dcy

stealth address amount amount idx
00: d7c848db577038021257ac08373777b0b5d50844584aa6a916c74ac7cdf38ea9 347.771387861000 137804 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": 74467, "vin": [ { "gen": { "height": 74457 } } ], "vout": [ { "amount": 347771387861, "target": { "key": "d7c848db577038021257ac08373777b0b5d50844584aa6a916c74ac7cdf38ea9" } } ], "extra": [ 1, 34, 237, 73, 107, 148, 62, 34, 78, 209, 170, 88, 94, 235, 230, 58, 194, 61, 115, 141, 217, 16, 127, 55, 245, 108, 129, 68, 234, 240, 140, 32, 95, 2, 17, 0, 0, 2, 51, 2, 107, 89, 243, 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