Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af4e7c12097bd5081bf3a27a241a951bd9687a2f1ca5809e9787aa18efacda43

Tx prefix hash: 659afa555526d84ab597c6539612a0fa64d0cf2a29fd198583d4e9c8fea2d710
Tx public key: bd5b0f8f1c107bacecd06003efee246da08e556d051ee4bc96aa6aee70f4f462
Timestamp: 1711602420 Timestamp [UCT]: 2024-03-28 05:07:00 Age [y:d:h:m:s]: 01:048:01:23:27
Block: 987954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295330 RingCT/type: yes/0
Extra: 01bd5b0f8f1c107bacecd06003efee246da08e556d051ee4bc96aa6aee70f4f4620211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a75bdf625c880410a18050d0e6655d4f48a25814b9030957f2b49d8567f7704 0.600000000000 1448215 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": 987964, "vin": [ { "gen": { "height": 987954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a75bdf625c880410a18050d0e6655d4f48a25814b9030957f2b49d8567f7704" } } ], "extra": [ 1, 189, 91, 15, 143, 28, 16, 123, 172, 236, 208, 96, 3, 239, 238, 36, 109, 160, 142, 85, 109, 5, 30, 228, 188, 150, 170, 106, 238, 112, 244, 244, 98, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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