Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 977d9107a16b9fd25c1039f1b2b5c92799c34fb816ee509374b6b65a919ae7d8

Tx prefix hash: 65d96449f174c910ac65b1988adb6c1ae19755b1f35df9e2a76554076dd7cf18
Tx public key: 1426b3ab25208d6f1206db4807e85a8de43b95316051d64eb071fe40136bc8ff
Timestamp: 1728987630 Timestamp [UCT]: 2024-10-15 10:20:30 Age [y:d:h:m:s]: 00:161:11:48:15
Block: 1132068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115188 RingCT/type: yes/0
Extra: 011426b3ab25208d6f1206db4807e85a8de43b95316051d64eb071fe40136bc8ff021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2a6e58db62cdbd28783d44a4cb32259e2f57570c725e6d0acd0fcd907eed5d2 0.600000000000 1614977 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": 1132078, "vin": [ { "gen": { "height": 1132068 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2a6e58db62cdbd28783d44a4cb32259e2f57570c725e6d0acd0fcd907eed5d2" } } ], "extra": [ 1, 20, 38, 179, 171, 37, 32, 141, 111, 18, 6, 219, 72, 7, 232, 90, 141, 228, 59, 149, 49, 96, 81, 214, 78, 176, 113, 254, 64, 19, 107, 200, 255, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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