Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90527769aa5a78fbf1806f0f963e5bba20de11ac12cb4a712b6030416a132e07

Tx prefix hash: 8f0ed12fe32c77ee7c30569149b337390bd80f0d4655a1a05dc88ef82f942c52
Tx public key: af2d590d8d551bc219e66c94be3b71182d740d48eee6e430022a871ef3f3f8d4
Timestamp: 1703045281 Timestamp [UCT]: 2023-12-20 04:08:01 Age [y:d:h:m:s]: 01:161:00:49:36
Block: 916992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376266 RingCT/type: yes/0
Extra: 01af2d590d8d551bc219e66c94be3b71182d740d48eee6e430022a871ef3f3f8d4021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7934b09cb6cdccab40108f693d04da1b91f701f05c0f92106da1df31fae48459 0.600000000000 1374556 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": 917002, "vin": [ { "gen": { "height": 916992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7934b09cb6cdccab40108f693d04da1b91f701f05c0f92106da1df31fae48459" } } ], "extra": [ 1, 175, 45, 89, 13, 141, 85, 27, 194, 25, 230, 108, 148, 190, 59, 113, 24, 45, 116, 13, 72, 238, 230, 228, 48, 2, 42, 135, 30, 243, 243, 248, 212, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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