Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8b7bfc3c48213212a6aaa5c6b6a3fe2946d010fd7afcae2e0375a7039ddfdd3

Tx prefix hash: 79864f68ccaef2459113185c6cb3674a26e3fca9af65567dd6456727d0d37f7f
Tx public key: 3400318e1ae28db6e8c9aa941cbcc0d1c5aba3073300b589e21b16552aab557f
Timestamp: 1736150594 Timestamp [UCT]: 2025-01-06 08:03:14 Age [y:d:h:m:s]: 00:113:17:52:19
Block: 1191328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81087 RingCT/type: yes/0
Extra: 013400318e1ae28db6e8c9aa941cbcc0d1c5aba3073300b589e21b16552aab557f02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e095c142a133f6e3cf896f9b8d24debdc3e4ee1706cf7e4f6fff3cd7d33808f 0.600000000000 1677853 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": 1191338, "vin": [ { "gen": { "height": 1191328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e095c142a133f6e3cf896f9b8d24debdc3e4ee1706cf7e4f6fff3cd7d33808f" } } ], "extra": [ 1, 52, 0, 49, 142, 26, 226, 141, 182, 232, 201, 170, 148, 28, 188, 192, 209, 197, 171, 163, 7, 51, 0, 181, 137, 226, 27, 22, 85, 42, 171, 85, 127, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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