Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc1b484c7f629083f5d20e352e23ac019444234b99e94e31f9eacb2fd519bddb

Tx prefix hash: 8723e396a48728f288c80bc2e11e3f69ca3f2c5e1148c4f43351b94f7f75ff47
Tx public key: 11f1464881be5e669f11f40cd9d816fa75a5b4c4183f11a2ea0ea3c8d2d9c00a
Timestamp: 1736133425 Timestamp [UCT]: 2025-01-06 03:17:05 Age [y:d:h:m:s]: 00:162:13:21:10
Block: 1191178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115893 RingCT/type: yes/0
Extra: 0111f1464881be5e669f11f40cd9d816fa75a5b4c4183f11a2ea0ea3c8d2d9c00a02110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cb119741ace16591a6d6355774d04e6d92765dd277a406e80ee7edd26d2fda3 0.600000000000 1677701 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": 1191188, "vin": [ { "gen": { "height": 1191178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cb119741ace16591a6d6355774d04e6d92765dd277a406e80ee7edd26d2fda3" } } ], "extra": [ 1, 17, 241, 70, 72, 129, 190, 94, 102, 159, 17, 244, 12, 217, 216, 22, 250, 117, 165, 180, 196, 24, 63, 17, 162, 234, 14, 163, 200, 210, 217, 192, 10, 2, 17, 0, 0, 0, 13, 31, 10, 83, 235, 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