Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1912d4ac7b90859ed8d8ece3cf80ff664a1c0861a38fa095e49c3d78e33d6157

Tx prefix hash: b669eafe1bf4d1c9775e77c79825b0864c938da63ba4d0e33aedcbc88e238cc7
Tx public key: 3ec2c53ec163021a759de95752afd2284d2a94c8056ad9811e8fe8cb05ccc549
Timestamp: 1672804145 Timestamp [UCT]: 2023-01-04 03:49:05 Age [y:d:h:m:s]: 02:320:07:13:07
Block: 667153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 748325 RingCT/type: yes/0
Extra: 013ec2c53ec163021a759de95752afd2284d2a94c8056ad9811e8fe8cb05ccc54902110000000633af99f4000000000000000000

1 output(s) for total of 3.779593766000 dcy

stealth address amount amount idx
00: ae0f5863e03000508f9476a757278a9eee72f956970607eea4d81731b7c9e71b 3.779593766000 1108318 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": 667163, "vin": [ { "gen": { "height": 667153 } } ], "vout": [ { "amount": 3779593766, "target": { "key": "ae0f5863e03000508f9476a757278a9eee72f956970607eea4d81731b7c9e71b" } } ], "extra": [ 1, 62, 194, 197, 62, 193, 99, 2, 26, 117, 157, 233, 87, 82, 175, 210, 40, 77, 42, 148, 200, 5, 106, 217, 129, 30, 143, 232, 203, 5, 204, 197, 73, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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