Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4def6e08a944ed1d10fc5f8827fc8bfa575948907e3e378bf21992662cbab60d

Tx prefix hash: 6b1a9229f2ac95e07b29ce3590e4a619c7d2f5a40f2b0c03b072c60cdd6f97ae
Tx public key: 74615132a377104a4c09b335d866afe94a8f2e00a8560c19e56db067880a24a8
Timestamp: 1739486885 Timestamp [UCT]: 2025-02-13 22:48:05 Age [y:d:h:m:s]: 00:290:08:42:36
Block: 1218679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205291 RingCT/type: yes/0
Extra: 0174615132a377104a4c09b335d866afe94a8f2e00a8560c19e56db067880a24a8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 125f836d808d65d4cb1d67c02e3768db355ddc28c7819f8874cd4b1d83206a9e 0.600000000000 1705498 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": 1218689, "vin": [ { "gen": { "height": 1218679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "125f836d808d65d4cb1d67c02e3768db355ddc28c7819f8874cd4b1d83206a9e" } } ], "extra": [ 1, 116, 97, 81, 50, 163, 119, 16, 74, 76, 9, 179, 53, 216, 102, 175, 233, 74, 143, 46, 0, 168, 86, 12, 25, 229, 109, 176, 103, 136, 10, 36, 168, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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