Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47e4f44dd063c2a6535efa7dc0427915b739b213f1e4b7da03c483878fd9a8da

Tx prefix hash: 83c1ef85a5b0bde3dfcb10640290727ceff5ad72fcbe641e2088c051e4e460ba
Tx public key: 468516216631f96759a2ef05e8064bc88d5b8b9234d5a3f97058e576907953c3
Timestamp: 1716761774 Timestamp [UCT]: 2024-05-26 22:16:14 Age [y:d:h:m:s]: 00:181:17:42:36
Block: 1030718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130078 RingCT/type: yes/0
Extra: 01468516216631f96759a2ef05e8064bc88d5b8b9234d5a3f97058e576907953c302110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71a46d510290fea1f6d988a1a83b0e6780e07dc61f3d522d4a88d72e519c2bfd 0.600000000000 1498987 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": 1030728, "vin": [ { "gen": { "height": 1030718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71a46d510290fea1f6d988a1a83b0e6780e07dc61f3d522d4a88d72e519c2bfd" } } ], "extra": [ 1, 70, 133, 22, 33, 102, 49, 249, 103, 89, 162, 239, 5, 232, 6, 75, 200, 141, 91, 139, 146, 52, 213, 163, 249, 112, 88, 229, 118, 144, 121, 83, 195, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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